|
|
The objective of this group of documentation is to show how to map an NSD crash stack to application code within an agent. This can be helpful when you are trying to debug an application but want to lower the scope of debugging to save time.
|
This documentation will detail how to map an NSD crash stack to
where in your agent code the crash may be occurring. It will not
guarantee a root cause of the crash, but can help in narrowing down the
level of code to debug. Related
Processes
The following processes are related to agent
code executing and would be detailed in the crash stack header. - AMGR
Agent
Manager. Scheduled agents, agents that are set to run on the server, by
program documents, or through the domino console.
- ROUTER
Mail
Router. If the agent is set to run before new mail arrives then it will
run under this process.
- HTTP
Agents that are
executed by a URL connection or a Web Service provider.
- DIIOP
Java
applications which are using the NCSO.jar to communicate with the
Domino server via DIIOP.
- NNOTES
Notes Client
crash. Refers to agents running on the client.
- RUNJAVA
Java
plugins that run on the server. Creating applications to run under this
process are unsupported. But diagnosing the issue to rule out RUNJAVA
can help support assist you further.
Crash Stack diagnosing
The details on reading
the crash stack has been broken down by operating systems.
|